Skip to content

net: STD for dual-stream RHCOS 9/10 node migration network tests#4569

Open
azhivovk wants to merge 1 commit intoRedHatQE:mainfrom
azhivovk:std_hetro
Open

net: STD for dual-stream RHCOS 9/10 node migration network tests#4569
azhivovk wants to merge 1 commit intoRedHatQE:mainfrom
azhivovk:std_hetro

Conversation

@azhivovk
Copy link
Copy Markdown
Contributor

@azhivovk azhivovk commented Apr 23, 2026

STD for network connectivity tests on clusters with mixed RHCOS 9 and RHCOS 10 worker nodes.

Tests cover four network types (Linux bridge, localnet, primary UDN, primary network) verifying connectivity is preserved during live migration of the server VM.
Server VM migration is considered the more impactful scenario as it tests connectivity preservation from the endpoint holding the listening socket.
Both migration directions are covered within other existing tests.

Each network type has its own module with shared setup (NNCP, NAD) in the module-level preconditions.
The primary network tests share the module and
VM setup with the Linux bridge tests, as both use the same VMs.

jira-ticket: https://redhat.atlassian.net/browse/CNV-81981

Summary by CodeRabbit

  • Tests
    • Added end-to-end tests verifying active TCP and ICMP connectivity is preserved during live VM migrations between RHCOS 9 and RHCOS 10 worker nodes.
    • Coverage includes Linux bridge, primary network, localnet, and user-defined network setups; each exercises forward and reverse migrations with connectivity checks after each migration.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 23, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: f7e8b925-1368-426c-9de2-e4a683c09981

📥 Commits

Reviewing files that changed from the base of the PR and between ad0bebc and e4021af.

📒 Files selected for processing (7)
  • tests/network/l2_bridge/mixed_nodes/__init__.py
  • tests/network/l2_bridge/mixed_nodes/test_l2_bridge_connectivity_mixed_nodes.py
  • tests/network/l2_bridge/mixed_nodes/test_primary_network_connectivity_mixed_nodes.py
  • tests/network/localnet/mixed_nodes/__init__.py
  • tests/network/localnet/mixed_nodes/test_localnet_connectivity_mixed_nodes.py
  • tests/network/user_defined_network/mixed_nodes/__init__.py
  • tests/network/user_defined_network/mixed_nodes/test_udn_connectivity_mixed_nodes.py

📝 Walkthrough

Walkthrough

Adds four new pytest modules (one test each) that declare connectivity-preservation scenarios for live migrations of a server VM between RHCOS 9 and RHCOS 10 worker nodes across L2 bridge, primary, localnet, and user-defined network types. Each module sets __test__ = False and defines a Polarion-tagged test with step/expectation docstrings.

Changes

Cohort / File(s) Summary
Mixed-nodes connectivity tests
tests/network/l2_bridge/mixed_nodes/test_l2_bridge_connectivity_mixed_nodes.py, tests/network/l2_bridge/mixed_nodes/test_primary_network_connectivity_mixed_nodes.py, tests/network/localnet/mixed_nodes/test_localnet_connectivity_mixed_nodes.py, tests/network/user_defined_network/mixed_nodes/test_udn_connectivity_mixed_nodes.py
Added four new pytest modules (one test each). Each file sets __test__ = False, imports pytest, and defines a single Polarion-tagged test function: test_linux_bridge_connectivity_preserved_during_server_migration_between_rhcos9_and_rhcos10 (CNV-15949), test_primary_network_connectivity_preserved_during_server_migration_between_rhcos9_and_rhcos10 (CNV-15950), test_localnet_connectivity_preserved_during_server_migration_between_rhcos9_and_rhcos10 (CNV-15951), and test_udn_connectivity_preserved_during_server_migration_between_rhcos9_and_rhcos10 (CNV-15952). Tests are docstring-driven and perform node-selector updates, live migrations, waits, and connectivity checks. Review attention: disabled collection via __test__ = False and docstring-only guidance.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the main change: adding STD (system test definition) for network connectivity tests covering RHCOS 9/10 node migrations.
Description check ✅ Passed The description covers most required template sections with clear details about test scope, network types, migration strategy, and module organization. Jira ticket is properly referenced.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@azhivovk azhivovk changed the title net: Add STD for heterogeneous RHCOS 9/10 node migration network tests net: STD for dua-stream RHCOS 9/10 node migration network tests Apr 23, 2026
@azhivovk azhivovk changed the title net: STD for dua-stream RHCOS 9/10 node migration network tests net: STD for dual-stream RHCOS 9/10 node migration network tests Apr 23, 2026
@openshift-virtualization-qe-bot-3
Copy link
Copy Markdown
Contributor

Report bugs in Issues

Welcome! 🎉

This pull request will be automatically processed with the following features:

🔄 Automatic Actions

  • Reviewer Assignment: Reviewers are automatically assigned based on the OWNERS file in the repository root
  • Size Labeling: PR size labels (XS, S, M, L, XL, XXL) are automatically applied based on changes
  • Issue Creation: A tracking issue is created for this PR and will be closed when the PR is merged or closed
  • Branch Labeling: Branch-specific labels are applied to track the target branch
  • Auto-verification: Auto-verified users have their PRs automatically marked as verified
  • Labels: Enabled categories: branch, can-be-merged, cherry-pick, has-conflicts, hold, needs-rebase, size, verified, wip

📋 Available Commands

PR Status Management

  • /wip - Mark PR as work in progress (adds WIP: prefix to title)
  • /wip cancel - Remove work in progress status
  • /hold - Block PR merging (approvers only)
  • /hold cancel - Unblock PR merging
  • /verified - Mark PR as verified
  • /verified cancel - Remove verification status
  • /reprocess - Trigger complete PR workflow reprocessing (useful if webhook failed or configuration changed)
  • /regenerate-welcome - Regenerate this welcome message

Review & Approval

  • /lgtm - Approve changes (looks good to me)
  • /approve - Approve PR (approvers only)
  • /assign-reviewers - Assign reviewers based on OWNERS file
  • /assign-reviewer @username - Assign specific reviewer
  • /check-can-merge - Check if PR meets merge requirements

Testing & Validation

  • /retest tox - Run Python test suite with tox
  • /retest build-container - Rebuild and test container image
  • /retest verify-bugs-are-open - verify-bugs-are-open
  • /retest all - Run all available tests

Container Operations

  • /build-and-push-container - Build and push container image (tagged with PR number)
    • Supports additional build arguments: /build-and-push-container --build-arg KEY=value

Cherry-pick Operations

  • /cherry-pick <branch> - Schedule cherry-pick to target branch when PR is merged
    • Multiple branches: /cherry-pick branch1 branch2 branch3

Label Management

  • /<label-name> - Add a label to the PR
  • /<label-name> cancel - Remove a label from the PR

✅ Merge Requirements

This PR will be automatically approved when the following conditions are met:

  1. Approval: /approve from at least one approver
  2. LGTM Count: Minimum 2 /lgtm from reviewers
  3. Status Checks: All required status checks must pass
  4. No Blockers: No wip, hold, has-conflicts labels and PR must be mergeable (no conflicts)
  5. Verified: PR must be marked as verified

📊 Review Process

Approvers and Reviewers

Approvers:

  • EdDev

Reviewers:

  • Anatw
  • EdDev
  • azhivovk
  • frenzyfriday
  • nirdothan
  • orelmisan
  • servolkov
  • yossisegev
Available Labels
  • hold
  • verified
  • wip
  • lgtm
  • approve
AI Features
  • Cherry-Pick Conflict Resolution: Enabled (claude/claude-opus-4-6[1m])

💡 Tips

  • WIP Status: Use /wip when your PR is not ready for review
  • Verification: The verified label is removed on new commits unless the push is detected as a clean rebase
  • Cherry-picking: Cherry-pick labels are processed when the PR is merged
  • Container Builds: Container images are automatically tagged with the PR number
  • Permission Levels: Some commands require approver permissions
  • Auto-verified Users: Certain users have automatic verification and merge privileges

For more information, please refer to the project documentation or contact the maintainers.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@tests/network/l2_bridge/mixed_nodes/test_primary_network_connectivity_mixed_nodes.py`:
- Around line 19-45: The Polarion marker value is duplicated (CNV-0) in the test
function
test_connectivity_over_primary_network_preserved_during_source_migration (and
across other mixed_nodes test modules), causing ambiguous test attribution;
update the pytest.mark.polarion decorator on this function to a unique
placeholder ID (e.g., CNV-0A) and ensure the other mixed_nodes modules
(functions with the same decorator such as in
test_l2_bridge_connectivity_mixed_nodes.py,
test_localnet_connectivity_mixed_nodes.py, test_udn_connectivity_mixed_nodes.py)
each get distinct placeholders (CNV-0B/C/D) or their final real Polarion IDs so
each test function has a unique polarion marker.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 695c7508-c3b6-4e04-aa6d-4fd9fd030b7e

📥 Commits

Reviewing files that changed from the base of the PR and between 0feeb8f and abcfaaa.

📒 Files selected for processing (7)
  • tests/network/l2_bridge/mixed_nodes/__init__.py
  • tests/network/l2_bridge/mixed_nodes/test_l2_bridge_connectivity_mixed_nodes.py
  • tests/network/l2_bridge/mixed_nodes/test_primary_network_connectivity_mixed_nodes.py
  • tests/network/localnet/mixed_nodes/__init__.py
  • tests/network/localnet/mixed_nodes/test_localnet_connectivity_mixed_nodes.py
  • tests/network/user_defined_network/mixed_nodes/__init__.py
  • tests/network/user_defined_network/mixed_nodes/test_udn_connectivity_mixed_nodes.py

@openshift-virtualization-qe-bot
Copy link
Copy Markdown

D/S test tox -e verify-tc-requirement-polarion failed: cnv-tests-tox-executor/27150

@azhivovk
Copy link
Copy Markdown
Contributor Author

Change: remove client migration scenarios

@openshift-virtualization-qe-bot
Copy link
Copy Markdown

D/S test tox -e verify-tc-requirement-polarion failed: cnv-tests-tox-executor/27258

@azhivovk
Copy link
Copy Markdown
Contributor Author

Change:

  • Update STP doc
  • Rename source-target VMs to client-server

@openshift-virtualization-qe-bot
Copy link
Copy Markdown

D/S test tox -e verify-tc-requirement-polarion failed: cnv-tests-tox-executor/27284

Copy link
Copy Markdown
Contributor

@nirdothan nirdothan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

coderabbitai[bot]
coderabbitai Bot previously approved these changes Apr 28, 2026
STD for network connectivity tests on clusters with
mixed RHCOS 9 and RHCOS 10 worker nodes.

Tests cover four network types (Linux bridge, localnet,
primary UDN, primary network) verifying connectivity is
preserved during live migration of the server VM.
Server VM migration is considered the more impactful scenario
as it tests connectivity preservation from the endpoint holding
the listening socket.
Both migration directions are covered within other
existing tests.

Each network type has its own module with shared setup
(NNCP, NAD) in the module-level preconditions.
The primary network tests share the module and
VM setup with the Linux bridge tests, as both use the same VMs.

Signed-off-by: Asia Khromov <azhivovk@redhat.com>
Assisted-by: Claude Sonnet 4.6
@azhivovk
Copy link
Copy Markdown
Contributor Author

Change: Add polarion IDs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants